LCP restriction enhancement

ABSTRACT

Aspects for enhanced logical channel prioritization mapping procedures and restrictions are disclosed. In one aspect, a method of wireless communication includes receiving, by a user equipment (UE), a logical channel prioritization (LCP) restriction configuration for a logical channel indicating a set of SRS configurations associated with the logical channel; receiving, by the UE, an uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; and selecting, by the UE, the logical channel to use resources of the uplink grant instance based in part on the set of SRS configurations and the SRS configuration for the uplink grant instance. Additional aspects are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/884,067, entitled, “LCP RESTRICTION ENHANCEMENT,”filed on Aug. 7, 2019, which is expressly incorporated by referenceherein in its entirety.

BACKGROUND Field

Aspects of the present disclosure relate generally to wirelesscommunication systems, and more particularly, to logical channelprioritization (LCP) enhancements, such as for multiple transmissionreception point (TRP) modes.

Background

Wireless communication networks are widely deployed to provide variouscommunication services such as voice, video, packet data, messaging,broadcast, and the like. These wireless networks may be multiple-accessnetworks capable of supporting multiple users by sharing the availablenetwork resources. Such networks, which are usually multiple accessnetworks, support communications for multiple users by sharing theavailable network resources. One example of such a network is theUniversal Terrestrial Radio Access Network (UTRAN). The UTRAN is theradio access network (RAN) defined as a part of the Universal MobileTelecommunications System (UMTS), a third generation (3G) mobile phonetechnology supported by the 3rd Generation Partnership Project (3GPP).Examples of multiple-access network formats include Code DivisionMultiple Access (CDMA) networks, Time Division Multiple Access (TDMA)networks, Frequency Division Multiple Access (FDMA) networks, OrthogonalFDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA) networks.

A wireless communication network may include a number of base stationsor node Bs that can support communication for a number of userequipments (UEs). A UE may communicate with a base station via downlinkand uplink. The downlink (or forward link) refers to the communicationlink from the base station to the UE, and the uplink (or reverse link)refers to the communication link from the UE to the base station.

A base station may transmit data and control information on the downlinkto a UE and/or may receive data and control information on the uplinkfrom the UE. On the downlink, a transmission from the base station mayencounter interference due to transmissions from neighbor base stationsor from other wireless radio frequency (RF) transmitters. On the uplink,a transmission from the UE may encounter interference from uplinktransmissions of other UEs communicating with the neighbor base stationsor from other wireless RF transmitters. This interference may degradeperformance on both the downlink and uplink.

As the demand for mobile broadband access continues to increase, thepossibilities of interference and congested networks grows with more UEsaccessing the long-range wireless communication networks and moreshort-range wireless systems being deployed in communities. Research anddevelopment continue to advance wireless technologies not only to meetthe growing demand for mobile broadband access, but to advance andenhance the user experience with mobile communications.

SUMMARY

The following summarizes some aspects of the present disclosure toprovide a basic understanding of the discussed technology. This summaryis not an extensive overview of all contemplated features of thedisclosure, and is intended neither to identify key or critical elementsof all aspects of the disclosure nor to delineate the scope of any orall aspects of the disclosure. Its sole purpose is to present someconcepts of one or more aspects of the disclosure in summary form as aprelude to the more detailed description that is presented later.

The described techniques relate to improved methods, systems, devices,and apparatuses that support enhanced logical channel prioritizationmapping procedures and restrictions, such as SRS/SRI (Sounding ReferenceSignal (SRS)/SRS Resource Indicator (SRI)) based indication of logicalchannel prioritization (LCP) restrictions. Such enhanced LCP mappingprocedures may enable operation in multiple TRP modes and/or mappingduplicate data for transmission via the same carrier. Accordingly, suchtechniques may increase reliability and reduce latency and enableoperation in URLLC modes.

In one aspect of the disclosure, a method of wireless communicationincludes receiving, by a user equipment (UE), a logical channelprioritization (LCP) restriction configuration for a logical channelindicating a set of SRS configurations associated with the logicalchannel; receiving, by the UE, an uplink grant indicating an uplinkgrant instance and an SRS configuration for the uplink grant instance;and selecting, by the UE, the logical channel to use resources of theuplink grant instance based in part on the set of SRS configurations andthe SRS configuration for the uplink grant instance.

In an additional aspect of the disclosure, an apparatus configured forwireless communication is disclosed. The apparatus includes at least oneprocessor, and a memory coupled to the processor. The processor isconfigured to receive, by a user equipment (UE), a logical channelprioritization (LCP) restriction configuration for a logical channelindicating a set of SRS configurations associated with the logicalchannel; receive, by the UE, an uplink grant indicating an uplink grantinstance and an SRS configuration for the uplink grant instance; andselect, by the UE, the logical channel to use resources of the uplinkgrant instance based in part on the set of SRS configurations and theSRS configuration for the uplink grant instance.

In another aspect of the disclosure, a method of wireless communicationincludes transmitting, by a network entity, a logical channelprioritization (LCP) restriction configuration for a logical channelindicating a set of SRS configurations associated with the logicalchannel; determining, by the network entity, data of the logical channelof a particular UE is to be scheduled; transmitting, by the networkentity, an uplink grant indicating an uplink grant instance for theparticular user device and an SRS configuration of the set of SRSconfigurations; and receiving, by the network entity, a transmissioncorresponding to the uplink grant instance and including the data of thelogical channel.

In an additional aspect of the disclosure, an apparatus configured forwireless communication is disclosed. The apparatus includes at least oneprocessor, and a memory coupled to the processor. The processor isconfigured to transmit, by a network entity, a logical channelprioritization (LCP) restriction configuration for a logical channelindicating a set of SRS configurations associated with the logicalchannel; determine, by the network entity, data of the logical channelof a particular UE is to be scheduled; transmit, by the network entity,an uplink grant indicating an uplink grant instance for the particularuser device and an SRS configuration of the set of SRS configurations;and receive, by the network entity, a transmission corresponding to theuplink grant instance and including the data of the logical channel.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentdisclosure may be realized by reference to the following drawings. Inthe appended figures, similar components or features may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 is a block diagram illustrating details of a wirelesscommunication system.

FIG. 2 is a block diagram illustrating a design of a base station and aUE configured according to one aspect of the present disclosure.

FIG. 3 is a diagram illustrating an example of a wireless communicationsystem that multi-transmission/reception point (TRP) schemes inaccordance with aspects of the present disclosure

FIG. 4 is a block diagram illustrating an example of a process flow thatsupport dynamic switching between different multi-TRP schemes inaccordance with aspects of the present disclosure.

FIGS. 5A-5D are diagrams illustrating different multi-TRP schemes andcorresponding PDCP PDU duplication for the different multi-TRP schemesin accordance with aspects of the present disclosure.

FIGS. 6A and 6B are diagrams illustrating uplink and downlink diagramsfor duplication and LCP for multi-TRP schemes in accordance with aspectsof the present disclosure.

FIG. 7 is a block diagram illustrating an example of a wirelesscommunications system that enables enhanced LCP mapping restrictions inaccordance with aspects of the present disclosure.

FIGS. 8A-8F are each a schematic diagram illustrating an example ofdownlink control message including fields thereof.

FIG. 9 is a block diagram illustrating example blocks executed by a UEconfigured according to an aspect of the present disclosure.

FIG. 10 is a block diagram illustrating example blocks executed by abase station configured according to an aspect of the presentdisclosure.

FIG. 11 is a block diagram conceptually illustrating a design of a UEaccording to some embodiments of the present disclosure.

FIG. 12 is a block diagram conceptually illustrating a design of a basestation configured according to some embodiments of the presentdisclosure.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to limit the scope of the disclosure.Rather, the detailed description includes specific details for thepurpose of providing a thorough understanding of the inventive subjectmatter. It will be apparent to those skilled in the art that thesespecific details are not required in every case and that, in someinstances, well-known structures and components are shown in blockdiagram form for clarity of presentation.

The detailed description is related to logical channel prioritization(LCP) enhancements. Conventionally, LCP is used by a UE to select alogical channel for uplink data. When operating in some multipletransmission reception point (TRP) modes, the UE may send data todifferent TRPs which have spatial diversity (e.g., have differentpositions due to different antenna equipment). The UE may send duplicatedata to increase throughput and reliability, such as to enable operationin URLLC modes. Because the data is duplicated, the LCP mappingrestrictions are unable to schedule and transmit copies/duplicates ofdate via the same carrier. To illustrate, in conventional operations,when the UE is attempting to map the duplicated data (e.g., two copiesof the same data) to separate logical channels for subsequent schedulingvia uplink grants, no mapping criteria is available to enable properselection of logical channels for proper transmission. For example, theUE cannot send the duplicated data via the logical channels becausethere may be no indication of transmission parameters (e.g., differenttransmission parameters) such that the two transmission can besuccessfully transmitted via the same carrier to two different TRPs.Thus, the UE uses different carriers to send the duplicate data in suchinstances. Such procedures may not achieve low latency requirements orconstraints for some operating modes, such as URLLC, (e.g., eURLLC).

The described techniques relate to improved methods, systems, devices,and apparatuses that support enhanced logical channel prioritizationmapping procedures and restrictions, such as SRS/SRI (Sounding ReferenceSignal (SRS)/SRS Resource Indicator (SRI)) based indication of logicalchannel prioritization (LCP) restrictions. Such enhanced LCP mappingprocedures may enable operation in multiple TRP modes and/or mappingduplicate data for transmission via the same carrier. Accordingly, suchtechniques may increase reliability and reduce latency and enableoperation in URLLC modes.

This disclosure relates generally to providing or participating inauthorized shared access between two or more wireless communicationssystems, also referred to as wireless communications networks. Invarious embodiments, the techniques and apparatus may be used forwireless communication networks such as code division multiple access(CDMA) networks, time division multiple access (TDMA) networks,frequency division multiple access (FDMA) networks, orthogonal FDMA(OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks,GSM networks, 5^(th) Generation (5G) or new radio (NR) networks, as wellas other communications networks. As described herein, the terms“networks” and “systems” may be used interchangeably.

An OFDMA network may implement a radio technology such as evolved UTRA(E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and thelike. UTRA, E-UTRA, and Global System for Mobile Communications (GSM)are part of universal mobile telecommunication system (UMTS). Inparticular, long term evolution (LTE) is a release of UMTS that usesE-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documentsprovided from an organization named “3rd Generation Partnership Project”(3GPP), and cdma2000 is described in documents from an organizationnamed “3rd Generation Partnership Project 2” (3GPP2). These variousradio technologies and standards are known or are being developed. Forexample, the 3rd Generation Partnership Project (3GPP) is acollaboration between groups of telecommunications associations thataims to define a globally applicable third generation (3G) mobile phonespecification. 3GPP long term evolution (LTE) is a 3GPP project whichwas aimed at improving the universal mobile telecommunications system(UMTS) mobile phone standard. The 3GPP may define specifications for thenext generation of mobile networks, mobile systems, and mobile devices.The present disclosure is concerned with the evolution of wirelesstechnologies from LTE, 4G, 5G, NR, and beyond with shared access towireless spectrum between networks using a collection of new anddifferent radio access technologies or radio air interfaces.

In particular, 5G networks contemplate diverse deployments, diversespectrum, and diverse services and devices that may be implemented usingan OFDM-based unified, air interface. In order to achieve these goals,further enhancements to LTE and LTE-A are considered in addition todevelopment of the new radio technology for 5G NR networks. The 5G NRwill be capable of scaling to provide coverage (1) to a massive Internetof things (IoTs) with an ultra-high density (e.g., ˜1M nodes/km²),ultra-low complexity (e.g., ˜10s of bits/sec), ultra-low energy (e.g.,˜10+ years of battery life), and deep coverage with the capability toreach challenging locations; (2) including mission-critical control withstrong security to safeguard sensitive personal, financial, orclassified information, ultra-high reliability (e.g., ˜99.9999%reliability), ultra-low latency (e.g., ˜1 ms), and users with wideranges of mobility or lack thereof; and (3) with enhanced mobilebroadband including extreme high capacity (e.g., ˜10 Tbps/km²), extremedata rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates),and deep awareness with advanced discovery and optimizations.

The 5G NR may be implemented to use optimized OFDM-based waveforms withscalable numerology and transmission time interval (TTI); having acommon, flexible framework to efficiently multiplex services andfeatures with a dynamic, low-latency time division duplex(TDD)/frequency division duplex (FDD) design; and with advanced wirelesstechnologies, such as massive multiple input, multiple output (MIMO),robust millimeter wave (mmWave) transmissions, advanced channel coding,and device-centric mobility. Scalability of the numerology in 5G NR,with scaling of subcarrier spacing, may efficiently address operatingdiverse services across diverse spectrum and diverse deployments. Forexample, in various outdoor and macro coverage deployments of less than3 GHz FDD/TDD implementations, subcarrier spacing may occur with 15 kHz,for example over 1, 5, 10, 20 MHz, and the like bandwidth. For othervarious outdoor and small cell coverage deployments of TDD greater than3 GHz, subcarrier spacing may occur with 30 kHz over 80/100 MHzbandwidth. For other various indoor wideband implementations, using aTDD over the unlicensed portion of the 5 GHz band, the subcarrierspacing may occur with 60 kHz over a 160 MHz bandwidth. Finally, forvarious deployments transmitting with mmWave components at a TDD of 28GHz, subcarrier spacing may occur with 120 kHz over a 500 MHz bandwidth.

The scalable numerology of the 5G NR facilitates scalable TTI fordiverse latency and quality of service (QoS) requirements. For example,shorter TTI may be used for low latency and high reliability, whilelonger TTI may be used for higher spectral efficiency. The efficientmultiplexing of long and short TTIs to allow transmissions to start onsymbol boundaries. 5G NR also contemplates a self-contained integratedsubframe design with uplink/downlink scheduling information, data, andacknowledgement in the same subframe. The self-contained integratedsubframe supports communications in unlicensed or contention-basedshared spectrum, adaptive uplink/downlink that may be flexiblyconfigured on a per-cell basis to dynamically switch between uplink anddownlink to meet the current traffic needs.

Various other aspects and features of the disclosure are furtherdescribed below. It should be apparent that the teachings herein may beembodied in a wide variety of forms and that any specific structure,function, or both being disclosed herein is merely representative andnot limiting. Based on the teachings herein one of an ordinary level ofskill in the art should appreciate that an aspect disclosed herein maybe implemented independently of any other aspects and that two or moreof these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. For example,a method may be implemented as part of a system, device, apparatus,and/or as instructions stored on a computer readable medium forexecution on a processor or computer. Furthermore, an aspect maycomprise at least one element of a claim.

FIG. 1 is a block diagram illustrating 5G network 100 including variousbase stations and UEs configured according to aspects of the presentdisclosure. The 5G network 100 includes a number of base stations 105and other network entities. A base station may be a station thatcommunicates with the UEs and may also be referred to as an evolved nodeB (eNB), a next generation eNB (gNB), an access point, and the like.Each base station 105 may provide communication coverage for aparticular geographic area. In 3GPP, the term “cell” can refer to thisparticular geographic coverage area of a base station and/or a basestation subsystem serving the coverage area, depending on the context inwhich the term is used.

A base station may provide communication coverage for a macro cell or asmall cell, such as a pico cell or a femto cell, and/or other types ofcell. A macro cell generally covers a relatively large geographic area(e.g., several kilometers in radius) and may allow unrestricted accessby UEs with service subscriptions with the network provider. A smallcell, such as a pico cell, would generally cover a relatively smallergeographic area and may allow unrestricted access by UEs with servicesubscriptions with the network provider. A small cell, such as a femtocell, would also generally cover a relatively small geographic area(e.g., a home) and, in addition to unrestricted access, may also providerestricted access by UEs having an association with the femto cell(e.g., UEs in a closed subscriber group (CSG), UEs for users in thehome, and the like). A base station for a macro cell may be referred toas a macro base station. A base station for a small cell may be referredto as a small cell base station, a pico base station, a femto basestation or a home base station. In the example shown in FIG. 1 , thebase stations 105 d and 105 e are regular macro base stations, whilebase stations 105 a-105 c are macro base stations enabled with one of 3dimension (3D), full dimension (FD), or massive MIMO. Base stations 105a-105 c take advantage of their higher dimension MIMO capabilities toexploit 3D beamforming in both elevation and azimuth beamforming toincrease coverage and capacity. Base station 105 f is a small cell basestation which may be a home node or portable access point. A basestation may support one or multiple (e.g., two, three, four, and thelike) cells.

The 5G network 100 may support synchronous or asynchronous operation.For synchronous operation, the base stations may have similar frametiming, and transmissions from different base stations may beapproximately aligned in time. For asynchronous operation, the basestations may have different frame timing, and transmissions fromdifferent base stations may not be aligned in time.

The UEs 115 are dispersed throughout the wireless network 100, and eachUE may be stationary or mobile. A UE may also be referred to as aterminal, a mobile station, a subscriber unit, a station, or the like. AUE may be a cellular phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, atablet computer, a laptop computer, a cordless phone, a wireless localloop (WLL) station, or the like. In one aspect, a UE may be a devicethat includes a Universal Integrated Circuit Card (UICC). In anotheraspect, a UE may be a device that does not include a UICC. In someaspects, UEs that do not include UICCs may also be referred to asinternet of everything (IoE) or internet of things (IoT) devices. UEs115 a-115 d are examples of mobile smart phone-type devices accessing 5Gnetwork 100 A UE may also be a machine specifically configured forconnected communication, including machine type communication (MTC),enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. UEs 115 e-115k are examples of various machines configured for communication thataccess 5G network 100. A UE may be able to communicate with any type ofthe base stations, whether macro base station, small cell, or the like.In FIG. 1 , a lightning bolt (e.g., communication links) indicateswireless transmissions between a UE and a serving base station, which isa base station designated to serve the UE on the downlink and/or uplink,or desired transmission between base stations, and backhaultransmissions between base stations.

In operation at 5G network 100, base stations 105 a-105 c serve UEs 115a and 115 b using 3D beamforming and coordinated spatial techniques,such as coordinated multipoint (CoMP) or multi-connectivity. Macro basestation 105 d performs backhaul communications with base stations 105a-105 c, as well as small cell, base station 105 f. Macro base station105 d also transmits multicast services which are subscribed to andreceived by UEs 115 c and 115 d. Such multicast services may includemobile television or stream video, or may include other services forproviding community information, such as weather emergencies or alerts,such as Amber alerts or gray alerts.

5G network 100 also support mission critical communications withultra-reliable and redundant links for mission critical devices, such UE115 e, which is a drone. Redundant communication links with UE 115 einclude from macro base stations 105 d and 105 e, as well as small cellbase station 105 f. Other machine type devices, such as UE 115 f(thermometer), UE 115 g (smart meter), and UE 115 h (wearable device)may communicate through 5G network 100 either directly with basestations, such as small cell base station 105 f, and macro base station105 e, or in multi-hop configurations by communicating with another userdevice which relays its information to the network, such as UE 115 fcommunicating temperature measurement information to the smart meter, UE115 g, which is then reported to the network through small cell basestation 105 f. 5G network 100 may also provide additional networkefficiency through dynamic, low-latency TDD/FDD communications, such asin a vehicle-to-vehicle (V2V) mesh network between UEs 115 i-115 kcommunicating with macro base station 105 e.

FIG. 2 shows a block diagram of a design of a base station 105 and a UE115, which may be one of the base station and one of the UEs in FIG. 1 .At the base station 105, a transmit processor 220 may receive data froma data source 212 and control information from a controller/processor240. The control information may be for the PBCH, PCFICH, PHICH, PDCCH,EPDCCH, MPDCCH etc. The data may be for the PDSCH, etc. The transmitprocessor 220 may process (e.g., encode and symbol map) the data andcontrol information to obtain data symbols and control symbols,respectively. The transmit processor 220 may also generate referencesymbols, e.g., for the PSS, SSS, and cell-specific reference signal. Atransmit (TX) multiple-input multiple-output (MIMO) processor 230 mayperform spatial processing (e.g., precoding) on the data symbols, thecontrol symbols, and/or the reference symbols, if applicable, and mayprovide output symbol streams to the modulators (MODs) 232 a through 232t. Each modulator 232 may process a respective output symbol stream(e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator232 may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal.Downlink signals from modulators 232 a through 232 t may be transmittedvia the antennas 234 a through 234 t, respectively.

At the UE 115, the antennas 252 a through 252 r may receive the downlinksignals from the base station 105 and may provide received signals tothe demodulators (DEMODs) 254 a through 254 r, respectively. Eachdemodulator 254 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator 254 may further process the input samples (e.g., for OFDM,etc.) to obtain received symbols. A MIMO detector 256 may obtainreceived symbols from all the demodulators 254 a through 254 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 258 may process (e.g., demodulate,deinterleave, and decode) the detected symbols, provide decoded data forthe UE 115 to a data sink 260, and provide decoded control informationto a controller/processor 280.

On the uplink, at the UE 115, a transmit processor 264 may receive andprocess data (e.g., for the PUSCH) from a data source 262 and controlinformation (e.g., for the PUCCH) from the controller/processor 280. Thetransmit processor 264 may also generate reference symbols for areference signal. The symbols from the transmit processor 264 may beprecoded by a TX MIMO processor 266 if applicable, further processed bythe modulators 254 a through 254 r (e.g., for SC-FDM, etc.), andtransmitted to the base station 105. At the base station 105, the uplinksignals from the UE 115 may be received by the antennas 234, processedby the demodulators 232, detected by a MIMO detector 236 if applicable,and further processed by a receive processor 238 to obtain decoded dataand control information sent by the UE 115. The processor 238 mayprovide the decoded data to a data sink 239 and the decoded controlinformation to the controller/processor 240.

The controllers/processors 240 and 280 may direct the operation at thebase station 105 and the UE 115, respectively. The controller/processor240 and/or other processors and modules at the base station 105 mayperform or direct the execution of various processes for the techniquesdescribed herein. The controllers/processor 280 and/or other processorsand modules at the UE 115 may also perform or direct the execution ofthe functional blocks illustrated in FIGS. 9 and 10 , and/or otherprocesses for the techniques described herein. The memories 242 and 282may store data and program codes for the base station 105 and the UE115, respectively. A scheduler 244 may schedule UEs for datatransmission on the downlink and/or uplink.

Wireless communications systems operated by different network operatingentities (e.g., network operators) may share spectrum. In someinstances, a network operating entity may be configured to use anentirety of a designated shared spectrum for at least a period of timebefore another network operating entity uses the entirety of thedesignated shared spectrum for a different period of time. Thus, inorder to allow network operating entities use of the full designatedshared spectrum, and in order to mitigate interfering communicationsbetween the different network operating entities, certain resources(e.g., time) may be partitioned and allocated to the different networkoperating entities for certain types of communication.

For example, a network operating entity may be allocated certain timeresources reserved for exclusive communication by the network operatingentity using the entirety of the shared spectrum. The network operatingentity may also be allocated other time resources where the entity isgiven priority over other network operating entities to communicateusing the shared spectrum. These time resources, prioritized for use bythe network operating entity, may be utilized by other network operatingentities on an opportunistic basis if the prioritized network operatingentity does not utilize the resources. Additional time resources may beallocated for any network operator to use on an opportunistic basis.

Access to the shared spectrum and the arbitration of time resourcesamong different network operating entities may be centrally controlledby a separate entity, autonomously determined by a predefinedarbitration scheme, or dynamically determined based on interactionsbetween wireless nodes of the network operators.

In some cases, UE 115 and base station 105 of the 5G network 100 (inFIG. 1 ) may operate in a shared radio frequency spectrum band, whichmay include licensed or unlicensed (e.g., contention-based) frequencyspectrum. In an unlicensed frequency portion of the shared radiofrequency spectrum band, UEs 115 or base stations 105 may traditionallyperform a medium-sensing procedure to contend for access to thefrequency spectrum. For example, UE 115 or base station 105 may performa listen before talk (LBT) procedure such as a clear channel assessment(CCA) prior to communicating in order to determine whether the sharedchannel is available. A CCA may include an energy detection procedure todetermine whether there are any other active transmissions. For example,a device may infer that a change in a received signal strength indicator(RSSI) of a power meter indicates that a channel is occupied.Specifically, signal power that is concentrated in a certain bandwidthand exceeds a predetermined noise floor may indicate another wirelesstransmitter. A CCA also may include detection of specific sequences thatindicate use of the channel. For example, another device may transmit aspecific preamble prior to transmitting a data sequence. In some cases,an LBT procedure may include a wireless node adjusting its own backoffwindow based on the amount of energy detected on a channel and/or theacknowledge/negative-acknowledge (ACK/NACK) feedback for its owntransmitted packets as a proxy for collisions.

In general, four categories of LBT procedure have been suggested forsensing a shared channel for signals that may indicate the channel isalready occupied. In a first category (CAT 1 LBT), no LBT or CCA isapplied to detect occupancy of the shared channel. A second category(CAT 2 LBT), which may also be referred to as an abbreviated LBT, asingle-shot LBT, or a 25-μs LBT, provides for the node to perform a CCAto detect energy above a predetermined threshold or detect a message orpreamble occupying the shared channel. The CAT 2 LBT performs the CCAwithout using a random back-off operation, which results in itsabbreviated length, relative to the next categories.

A third category (CAT 3 LBT) performs CCA to detect energy or messageson a shared channel, but also uses a random back-off and fixedcontention window. Therefore, when the node initiates the CAT 3 LBT, itperforms a first CCA to detect occupancy of the shared channel. If theshared channel is idle for the duration of the first CCA, the node mayproceed to transmit. However, if the first CCA detects a signaloccupying the shared channel, the node selects a random back-off basedon the fixed contention window size and performs an extended CCA. If theshared channel is detected to be idle during the extended CCA and therandom number has been decremented to 0, then the node may begintransmission on the shared channel. Otherwise, the node decrements therandom number and performs another extended CCA. The node would continueperforming extended CCA until the random number reaches 0. If the randomnumber reaches 0 without any of the extended CCAs detecting channeloccupancy, the node may then transmit on the shared channel. If at anyof the extended CCA, the node detects channel occupancy, the node mayre-select a new random back-off based on the fixed contention windowsize to begin the countdown again.

A fourth category (CAT 4 LBT), which may also be referred to as a fullLBT procedure, performs the CCA with energy or message detection using arandom back-off and variable contention window size. The sequence of CCAdetection proceeds similarly to the process of the CAT 3 LBT, exceptthat the contention window size is variable for the CAT 4 LBT procedure.

Use of a medium-sensing procedure to contend for access to an unlicensedshared spectrum may result in communication inefficiencies. This may beparticularly evident when multiple network operating entities (e.g.,network operators) are attempting to access a shared resource. In the 5Gnetwork 100, base stations 105 and UEs 115 may be operated by the sameor different network operating entities. In some examples, an individualbase station 105 or UE 115 may be operated by more than one networkoperating entity. In other examples, each base station 105 and UE 115may be operated by a single network operating entity. Requiring eachbase station 105 and UE 115 of different network operating entities tocontend for shared resources may result in increased signaling overheadand communication latency.

FIG. 3 illustrates an example of a wireless communications system 300that supports dynamic switching between different multi-TRP schemes inaccordance with aspects of the present disclosure. In some examples,wireless communications system 300 may implement aspects of wirelesscommunication system 100. For example, wireless communications system300 may include multiple UEs 115 and base stations 105. The basestations 105 may communicate with the UEs 115 using TRPs 305. Each basestation 105 may have one or more TRPs 305. For example, base station105-a may include TRP 305-a and TRP 305-b, while base station 105-b mayinclude TRP 305-c. UE 115-a may communicate with the network using asingle TRP 305, using multiple TRPs 305 corresponding to a single basestation 105 (e.g., TRPs 305-a and 305-b at base station 105-a), or usingmultiple TRPs 305 corresponding to multiple different base stations 105(e.g., TRP 305-a at base station 105-a and TRP 305-c at base station105-b, where base stations 105-a and 105-b may be connected via abackhaul connection).

In a communication scheme that includes multiple TRPs 305, a single DCImessage may configure the communications for the multiple TRPs 305. Inan example, base station 105-a may communicate using a first TRP 305-aand a second TRP 305-b. Base station 105-a may transmit DCI using TRP305-a on a PDCCH 310-a to UE 115-a. The DCI may include communicationconfiguration information for the TCI state(s). The TCI state(s) maydetermine whether the communications correspond to single TRPcommunication or multiple TRP communication. The TCI state(s) may alsoindicate the type of communication scheme (e.g., TDM, FDM, SDM, etc.)configured for the communication. If the TCI configuration is one TCIstate, the one TCI state may correspond to single TRP communication. Ifthe TCI configuration is multiple TCI states, the multiple TCI statesmay correspond to communication with multiple TRPs. In some cases, thewireless communications system 300 may support up to M candidate TCIstates for the purpose of quasi-co-location (QCL) indication. Of these Mcandidates (e.g., 128 candidate TCI states), a subset of TCI states maybe determined based on a medium access control (MAC) control element(CE). The MAC-CE may correspond to a certain number (e.g., 2^(N), suchas 8 TCI states) of candidate TCI states for PDSCH QCL indication. Oneof these 2^(N) TCI states can be dynamically indicated in a message(e.g., DCI) using N bits.

The DCI on the PDCCH 310-a may schedule PDSCH 315-a transmissions fromTRP 305-a for single TRP communication configurations. Alternatively,the DCI on the PDCCH 310-a may schedule multiple PDSCH 315 transmissionsfrom multiple TRPs 305. For example, the DCI may schedule PDSCH 315-atransmissions from TRP 305-a and PDSCH 315-b transmissions from TRP305-b or PDSCH 315-a transmissions from TRP 305-a and PDSCH 315-ctransmission from TRP 305-c for multiple TRP communicationconfigurations. A UE 115 may be configured with a list of differentcandidate TCI states for the purpose of QCL indication. The QCLindication may also indicate DMRS in the DCI corresponding to the PDSCH315. Each TCI code point in a DCI may correspond to one or more QCLrelationships (e.g., corresponding to one or more reference signal (RS)sets) and, accordingly, one or more TCI states.

In cases where the network communicates with a UE 115 with TRPs 305,whether in a single TRP configuration or a multiple TRP configuration,there may be multiple different schemes with which to communicate withthe TRP(s) 305. The TRP communication scheme may be determined by theTCI states. The TCI state(s) for communication on the PDSCH 315 may beindicated in the DCI by one or more bits, where the one or more bitsindicate a TCI code point. The TCI code point in the DCI can correspondto one or more TCI states (e.g., either one or two TCI states). If theTCI code point in the DCI indicates one TCI state, the UE 115 isconfigured for single TRP operation. If the TCI code point in the DCIindicates two TCI states (and, correspondingly, two QCL relationships),the UE 115 is configured for multiple TRP operation. For example, if twoTCI states are active within a TCI code point, each TCI state maycorrespond to one code division multiplexing (CDM) group.

In a first example multi-TRP scheme, TRPs 305 may communicate byutilizing SDM. In this case, different spatial layers may be transmittedfrom different TRPs 305 on the same RBs and symbols. Each TCI state mayalso correspond to different DMRS port groups. The DMRS ports in a DMRSCDM port group may be QCLed. This may allow a UE 115 to estimate eachchannel separately. In SDM, each antenna port used on the downlink maybelong to a different CDM group. Base station 105-a may indicate theantenna port groups using an antenna port(s) field in DCI.

The SDM scheme may include different TCI states within a single slot,where the TCI states overlap in time, frequency, or both. Differentgroups of spatial layers (which may correspond to different TCI states)may use the same modulation order. Cases where multiple groups use thesame modulation order may be signaled through the modulation and codingscheme (MCS). In some cases, base station 105-a may indicate the MCS inthe DCI. In cases where the different groups of spatial layers usedifferent modulation orders, each of the different modulation orders maybe signaled to UE 115-a. Different DMRS port groups may correspond todifferent TRPs, QCL relationships, TCI states, or a combination thereof.

In other examples of multi-TRP schemes, TRPs 305 may communicate with UE115-a by utilizing FDM and/or TDM communication schemes. In an FDMscheme, one set of RBs or a set of PRGs may correspond to a first TRP305-a and a first TCI state, and a second set of RBs or PRGs maycorrespond to a second TRP 305-b and a second TCI state. The RBsallocated for each TRP may be distinct from each other, so that each TRPcommunicates on a designated set of RBs that are distinct form the otherset of RBs (but may overlap in the same OFDM symbol). The frequencydomain resource assignment field in the DCI may indicate both the firstset and the second set or RBs or PRGs. In some cases, base station 105-amay use additional signaling in the DCI to indicate which RBs belong tothe first set and which belong to the second set. In some cases, thesystem may support a limited number of possibilities for allocating thefrequency resources to the different TRPs (e.g., to reduce theoverhead).

In a TDM scheme, a similar table of possibilities may be used to signalthe resource allocation for different TRPs. In this case, each TRP isallocated to different sets of OFDM symbols rather than to differentsets of RBs. Such a TDM scheme may support TDMed transmissions within asingle slot (e.g., transmission time interval (TTI)). In some cases, aTDM scheme may implement slot aggregation, where transmissions usingdifferent TCI states may be spread across different slots (e.g., TTIs).In slot aggregation, the transmissions over the different TRPs may useseparate rate matching, but may have the same or different modulationorders.

The network may communicate with UE 115-a using multiple TRPs and any ofthe communication schemes described herein. Further, some communicationschemes may include a combination of TDM and FDM, or cases where TDM mayor may not be in a slot aggregation configuration. The schemes may alsoinclude some cases where rate matching is joint and some cases whererate matching is separate for different TRPs, and the schemes may alsoinclude cases where the different TRPs have the same or differentmodulation orders. Each scheme may also utilize different parametersthat are included in signaling, such as which DMRS ports are used (e.g.,for an SDM scheme) or how RBs are split up (e.g., for an FDM scheme).

To efficiently configure UE 115-a with the TCI state information—and thecorresponding TRP scheme—base station 105-a may generate bits for a DCImessage and may transmit the DCI on PDCCH 310-a. The DCI message may betransmitted to UE 115-a using TRP 305-a. UE 115-a may determine whichscheme is configured for communication with TRPs 305 based on one ormore fields of the received DCI. The DCI may be the same size across allcommunication schemes, and the formatting (e.g., number of bits) of DCIfields may remain the same across the communication schemes.

In a first implementation, UE 115-a may detect the communication schemebased on the antenna port(s) field and the TCI field of the received DCImessage. The TCI field of the DCI may signify whether communication withone TRP using one TCI state is configured (e.g., TRP 305-a) orcommunication with multiple TRPs using multiple TCI states is configured(e.g., TRP 305-a and TRP 305-b). For example, a value (e.g.,tci-PresentInDCI) in the TCI field may not be configured for the CORESETscheduling the PDSCH, or the value may correspond to one TCI state. TheMAC-CE may configure the TCI state possibilities, and the TCI statefield of the DCI may indicate the possibility based on the configurationby the MAC-CE. Different values in the TCI state field may correspond toeither single TRP communication (e.g., communication with TRP 305-a if asingle TCI state is indicated) or multiple TRP communication (e.g.,communication with TRPs 305-a and 305-b, 305-a and 305-c, etc. if twoTCI states are indicated).

UE 115-a may determine whether the DCI indicates a single TRPcommunication scheme or a multiple TRP communication scheme based on thevalue in the TCI field and may interpret the value in the antennaport(s) field of the DCI based on the TCI field value. In cases wherethe TCI field corresponds to a communication scheme with a single TRP305, such as TRP 305-a, the UE 115-a may identify the value of theantenna port(s) field for a single TCI state. Based on a table inmemory, UE 115-a may determine one or more antenna ports for thescheduled PDSCH 315-a transmission based on the antenna port(s) fieldvalue. In cases where the TCI field corresponds to a communicationscheme with multiple TRPs 305, such as TRP 305-a and TRP 305-b, the UE115-a may identify the value of the antenna port(s) field and determinea multi-TRP scheme based on the value. In an example, the antennaport(s) field value may correspond to one or more DMRS ports, acommunication scheme, a rate matching configuration, scheme-specificparameters, or some combination of these.

In a second implementation, the UE 115-a may determine the communicationscheme based on a field explicitly indicating the scheme in a DCImessage (e.g., a multi-TCI-scheme field). The value in the multi-TCIscheme field may correspond to a specific multi-TCI scheme (e.g., SDM,FDM, or TDM). If the value in the multi-TCI scheme field corresponds toa TDM scheme, the value may additionally indicate if the TDM scheme isconfigured for one slot or for multiple slots based on a slotaggregation procedure.

In one example, the UE 115-a may identify a value for the TCI field inthe DCI message and may determine whether the communication schemeincludes multiple TCI states based on the TCI field value. If the valuedoes not correspond to multiple TCI states, then the UE 115-a may ignore(e.g., not process) the multi-TCI state field. In some cases, the valueof the multi-TCI scheme field may only be relevant in cases where theTCI field in the DCI corresponds to more than one TCI state.

In a second example, the UE 115-a may determine whether thecommunication scheme includes multiple TCI states based on the multi-TCIstate field. For example, a particular value of the multi-TCI statefield may correspond to a single TCI state, while the other values maycorrespond to different multiple TCI scheme possibilities. In thisexample, the UE 115-a may interpret the TCI field based on whether themulti-TCI state field indicates single or multiple TRP operation. Forexample, the same TCI code point in the TCI field may correspond toeither one TCI state or a pair of TCI states based on whether themulti-TCI state field indicates single or multiple TRP operation. Inthis way, a three-bit TCI field may support eight different single TCIstate options and eight different pairs for multiple TCI state options.

The UE 115-a may interpret the value received in the multi-TCI statefield based on a table. For example, the value may indicate a certainTRP communication scheme, a rate matching configuration, one or morescheme specific parameters, a modulation order, or any combination ofthese.

In some cases, different modulation orders are used in different TCIstates. The table referenced above may include an additional oralternative column indicating a modulation order for the second TCIstate in a multi-TCI scheme. This modulation order value may be anabsolute modulation order or may be a relative modulation order withrespect to modulation order for the first TCI state in the multi-TCIscheme.

In some cases, the UE 115-a may interpret the antenna port(s) field inthe DCI message based on the multi-TCI scheme field. In some examples,UE 115-a may determine based on the two fields that a single TRPconfiguration is used, or that a multiple TRP configuration with TDM orFDM is used. In these examples, UE 115-a may determine the antenna portsscheme based on a table supporting a single TCI state (or based on noSDM). In other examples, UE 115-a may determine that a multiple TRPconfiguration with SDM is used. In these other examples, UE 115-a maydetermine the antenna ports scheme based on a table supporting multipleantenna ports for multiple TCI states.

In other cases, the UE 115-a may use both the antenna port(s) field andthe multi-TCI scheme field to determine the communication scheme. Forexample, UE 115-a may determine whether the multi-TCI scheme is an SDMscheme based on the antenna port(s) field. If not, UE 115-a maydetermine whether the multi-TCI scheme is an FDM or TDM scheme based onthe multi-TCI scheme field.

In a third implementation, the UE 115-a may determine RVs for the PDSCH315 transmissions based on the DCI. For example, base station 105-a mayidentify a transport block for transmission to UE 115-a. Base station105-a may encode the transport block and transmit coded bits using TRP305-a and TRP 305-b. If base station 105-a performs joint rate matching,the coded bits for both TCI states may be the same, corresponding to oneRV. If base station 105-a performs separate rate matching, the codedbits for each TCI state may be different, corresponding to two differentRVs. Base station 105-a may indicate the one or more RVs in the singleDCI message on the PDCCH 310-a. If indicating one RV (e.g., for a singleTCI operation or when performing joint rate matching), base station105-a may indicate the one RV in an RV field in the DCI. If indicatingmultiple (e.g., two) RVs, base station 105-a may indicate a pair of RVsin one or more DCI fields.

In a first example, a first RV may be indicated in the RV field of theDCI and a second RV may be indicated in another field in the DCI. Forexample, the second RV may be indicated in the antenna port(s) field ofthe DCI, the multi-TCI scheme field of the DCI, or some combination ofthese.

In a second example, the antenna port(s) field or the multi-TCI schemefield of the DCI as described herein may indicate a rate matchingconfiguration. If the UE 115-a determines that the base station 105-aperformed separate rate matching, the UE 115-a may interpret the valuein the RV field to indicate separate RV values for the different TCIstates. For example, the value of the RV field may correspond to an RVpair, where the first RV value in the pair may correspond to a first TCIstate and the second RV value in the pair may correspond to a second TCIstate. The value-to-RV pair correspondence may be specified in a table(e.g., a lookup table). This table may be pre-configured in memory atthe UE 115-a and base station 105-a, or the network may configure UE115-a with the table.

In a third example, the rate matching configuration may also beindicated in the RV field. For example, the value of the RV field maycorrespond to either a single RV or multiple RVs, as shown in theexample RV table below. In some cases, UE 115-a may use this table tointerpret the RV field when determining that a multi-TRP scheme isconfigured. This table may be specified as a lookup table and may bepre-configured or dynamically configured by the network. If the value ofthe RV field corresponds to a single RV value for multi-TRP operation,UE 115-a may determine that the base station 105-a is performing jointrate matching. If the value of the RV field corresponds to a pair of RVvalues for multi-TRP operation, UE 115-a may determine that the basestation 105-a is performing separate rate matching.

In a fourth implementation, the UE 115-a may determine how to interpretan indication of PRG size in the DCI based on the configured multi-TRPscheme. If the UE 115-a determines that the multi-TCI scheme is an FDMscheme (e.g., based on either the antenna port(s) field or the multi-TCIfield), then the UE 115-a may interpret the PRB bundling size indicatorfield in the DCI per TCI state, as opposed to per bandwidth part. Forexample, if the PRB bundling size indicator field indicates widebandprecoding, the wideband precoding configuration may include widebandcommunication only within RBs associated with a same TCI state.

It is to be understood that wireless communications system 300 mayimplement any combination of the implementations described herein todynamically signal the TCI states for a selected multi-TRP scheme in asingle DCI message.

FIG. 4 illustrates an example of a process flow 400 that supportsdynamic switching between different multi-TRP schemes in accordance withaspects of the present disclosure. In some examples, process flow 400may implement aspects of a wireless communications system 100 or 300.For example, a base station 105 and UE 115, such as base station 105-cand UE 115-b, may perform one or more of the processes described withreference to process flow 400. Base station 105-c may communicate withUE 115-b by transmitting and receiving signals through TRPs 405-a and405-b. In other cases, TRPs 405-a and 405-b may correspond to differentbase stations 105. Alternative examples of the following may beimplemented, where some steps are performed in a different order thandescribed or are not performed at all. In some cases, steps may includeadditional features not mentioned below, or further steps may be added.

At 410, base station 105-c may generate DCI. The generation may includegenerating a first set of bits (e.g., a TCI field) that may indicate aset of TCI states for communication with UE 115-b. The generation mayalso include generating a second set of bits (e.g., an antenna port(s)field) that may indicate a set of antenna ports and, in some cases, amulti-TRP communication scheme for multiple TRP communication operation.In some cases, the second set of bits may additionally indicate amodulation order for at least one TCI state (e.g., a second TCI statefor TRP 405-b), an RV for a TB for at least one TCI state (e.g., thesecond TCI state for TRP 405-b), or a combination thereof.

At 415, base station 105-c may transmit the generated DCI to UE 115-b.UE 115-b may receive the DCI from base station 105-c. The DCI may betransmitted on a PDCCH from TRP 405-a. The DCI may schedule upcomingPDSCH transmissions and may include other control information. The DCImay include an indication of the first set of bits and the second set ofbits. For example, the DCI may include coded bits based on the first setof bits and the second set of bits.

At 420, UE 115-b may read the TCI field (e.g., the first set of bits)received in the DCI message. UE 115-b may identify, using the first setof bits, one or more TCI states for communication with base station105-c using one or more TRPs 405.

At 425, UE 115-b may determine the TCI state configuration based onreading the TCI field of the DCI. For example, a value (e.g.,tci-PresentInDCI) in the TCI field may not be configured for the CORESETscheduling the PDSCH, or the value may correspond to one TCI state. Inthese cases, the communication scheme may be configured for one TRP. Inother cases, the TCI field value may correspond to more than one TCIstate. In these other cases, the communication may be configured forcommunication with multiple TRPs.

UE 115-b may read the antenna port(s) field of the DCI and may interpretthe value of the field based on the determined TCI state configuration.For example, if UE 115-b determines that the TCI field indicates asingle TCI state, UE 115-b may identify, using the second set of bits, aset of antenna ports for the PDSCH transmission. At 430, UE 115-b mayaccess a table (e.g., pre-configured in memory or configured by thenetwork) to determine one or more antenna ports corresponding to theantenna port(s) field value.

Alternatively, if UE 115-b determines that the TCI field indicatesmultiple TCI states, UE 115-b may identify, using the second set ofbits, a set of antenna ports and a multi-TRP communication scheme basedon identifying the set of TCI states. The second set of bits may includethe same number of bits whether the field indicates just the set ofantenna ports for single TRP operation or the set of antenna ports andthe multi-TRP scheme for multi-TRP operation. At 430, UE 115-b mayaccess a lookup table to determine the set of antenna ports andmulti-TRP scheme based on the antenna port(s) field value. In somecases, UE 115-b may select the lookup table from a set of lookup tables,where the set may include one lookup table to use for single TRPoperation and one lookup table to use for multiple TRP operation.

The lookup table may include information mapping both the set of antennaports and the multiple TRP scheme to the second set of bits. In somecases, the lookup table mapping both the set of antenna ports and themultiple TRP communication scheme to the second set of bits may bepreconfigured in memory, and in some cases it may be dynamicallyconfigured by base station 105-c. UE 115-b may identify the second setof antenna ports and multiple TRP schemes based on the selected lookuptable. In the lookup table for multi-TRP operation, along withindications of the DMRS ports, the table may include indications of themultiple TRP scheme (e.g., SDM, FDM, TDM, or some combination thereof).The antenna port(s) field lookup table may indicate that a value in theantenna port(s) field of the DCI corresponds to a set of DMRS ports,where the set of DMRS ports further corresponds to a communicationscheme, such as SDM or FDM. The antenna port(s) field value may alsoindicate if rate matching is joint or separate. If the antenna port(s)field value indicates the use of an FDM communication scheme, the tablemay additionally indicate an RB configuration for the FDMed TCI states,as shown in the “Possibility” column of the table below. If the lookuptables are configurable by the network, then the network may define thesets of possible DMRS ports and the type of schemes using radio resourcecontrol (RRC) signaling.

In some cases, UE 115-b may identify, using the second set of bits, amodulation order for at least one TCI state of the set of possible TCIstates. Different modulation orders may also be used across differentTCI states. A first modulation order may be indicated in a modulationorder field. The first modulation order may correspond to a first TCIstate in a multi-TRP operation. A second modulation order may beindicated in one of the tables above based on the received value for theantenna port(s) field. For example, a column in the antenna port(s)field lookup table may indicates if the modulation order correspondingto the second TCI state is the same as the modulation order indicated inthe MCS (i.e., the modulation order for the first TCI state). If themodulation order is not the same as the modulation order indicated inthe MCS, then the value of the modulation order for the second TCI statemay be indicated in the antenna port(s) field. The value of themodulation order may be an absolute value or may be a relative valuewith respect to the first modulation order.

If the TCI state configuration is determined to indicate communicationwith a single TRP, then UE 115-b may send or receive a transmission fromone TRP 405-a at 435. UE 115-b may communicate with the single TRP 405-abased on the determined communication scheme. In some aspects, sendingto a TRP may involve using transmission configuration parameters (e.g.,beam, spatial filter configuration) suited for reception using the TRP.

If the TCI state configuration is determined to indicate communicationwith multiple TRPs 405, UE 115-b may send or receive a transmission fromone TRP 405-a at 435 and may also send or receive a transmission fromanother TRP 405-b at 440 (where, in some cases, 435 and 440 maycorrespond to a same time or OFDM symbol). UE 115-b may communicate withthe network via the multiple configured TRPs 405 based on the determinedcommunication scheme. In some aspects, sending to a set of TRPs mayinvolve using transmission configuration parameters (e.g., beam, spatialfilter configuration) suited for reception using the set of TRPs.

Systems and methods described herein are directed to enhanced LCPmapping restrictions such that a UE has enhanced functionality. Theenhanced functionality may enable operation in multi-TRP modes and/orduplication of data (e.g., PDCP PDUs). In a particular implementation,the systems and methods described herein enable PDCP PDU duplications tobe sent to different TRPs using the same carrier. Accordingly, suchsystems and methods can be utilized for URLLC and/or Multiple TRP modes.

Referring to FIGS. 5A-5D, examples of duplication for different multipleTRP modes are illustrated. FIGS. 5A and 5C correspond to diagrams forcarrier aggregation multiple TRP modes and FIGS. 5B and 5D correspond todiagrams for dual connectivity multiple TRP modes. In FIG. 5A, a diagramillustrating carrier aggregation is illustrated. FIG. 5A depicts onebase station 105 a which communicates with UE 115 a. Base station 105 amay transmit data and control information; base station 105 may transmit(and receive) information using different equipment and/or settings(e.g., different frequencies). In FIG. 5B, a diagram illustrating dualconnectivity is illustrated. FIG. 5B depicts two base stations, 105 aand 105 b which communicate with UE 115 a. UE 115 a communicates datawith both base stations and control information with one base station,main base station 105 a,

FIGS. 5C and 5D depict block diagrams of a UE stack. The UE stack (e.g.,user plane protocol stack) includes a Service Data Adaptation Protocol(SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a RadioLink Control (RLC) layer, a Medium Access Control (MAC) layer, and aPhysical (PHY) layer. The SDAP layer is configured to provide a mappingbetween QoS flow and a data radio bearer, marking QoS Flow ID (QFI) inboth uplink and downlink. A single SDAP (e.g., single SDAP entity) maybe configured for each Protocol Data Unit (PDU) session in some schemes.In Dual Connective (DC), two SDAP entities may be configured, such astwo stacks.

The PDCP layer is configured to perform services and functions thatinclude sequence numbering, transfer of user data, reordering andduplicate detection, PDCP PDU routing (e.g., for split bearers),retransmission of PDCP SDUs, and duplication of PDCP PDUs. The RLC layeris configured to perform services and functions that include thetransfer of upper layer PDUs, sequence numbering, segmentation andre-segmentation.

The MAC layer is configured to perform services and functions thatinclude mapping between logical channels (LCHs) and transport channels,multiplexing and demultiplexing of MAC SDUs, and logical channelprioritization. A single logical channel may be mapped to one or morenumerologies and/or TTI durations. For example, in LCP, the MAC layer(e.g., one MAC entity of the layer) determines a TTI duration ornumerology from the physical layer.

The MAC layer provides services to the RLC layer in the form of logicalchannels. A logical channel is defined by the type of data/informationit carries and is generally referred to as a control channel and usedfrom transmission of control and/or configuration or as a trafficchannel used for user data. The PHY layer is configured to performservices and functions that include mapping between transport channelsand physical channels.

Referring to FIGS. 5C and 5D, two example user plane stacks areillustrated. FIG. 5C depicts a user plane stack of a UE 115 foroperating in a multi-TRP carrier aggregation mode, and FIG. 5D depicts auser plane stack of a UE 115 for operating in a multi-TRP carrier dualconnectivity mode.

Referring to FIG. 5C, user plane stack includes a SDAP entity 512, aPDCP entity 522, a first RLC entity 532, a second RLC entity 534, and aMAC entity 542. The MAC entity includes a scheduler 552 and two HARQentities 562, 564.

During operation, the SDAP entity 512 generates a PDCP SDU 580 andtransmits the PDCP SDU 580 to the PDCP entity 522. The PDCP entity 522generates a PDCP header 590 and combines the PDCP header 590 and thePDCP SDU 580 to generate a first PDCP PDU 592. The PDCP entity 522duplicates the first PDCP PDU 592 to generate the second PDCP PDU 594.The PDCP entity 522 transmits the two PDCP PDUs 592, 594 tocorresponding RLC entities 532, 534. The RLC entities 532, 534 mayperform RLC operations on the PDCP PDUs 592, 594, such as addcorresponding RLC headers. The RLC 532, 534 entities transport the PDCPPDUs 592, 594 (e.g., RLC modified PDCP PDUs) to the MAC entity 542.

The scheduler 552 determines in which uplink grant to send each PDCP PDU592, 594. For example, the scheduler 552 receives two uplink grants anddetermines to send the first PDCP PDU 592 in the first uplink grant andthe second PDCP PDU 594 in the second uplink grant. The scheduler 552may perform LCP mapping procedure using LCP mapping restrictions. Insome such implementations, the scheduler 552 may perform enhanced LCPmapping or use “enhanced” LCP mapping restrictions, e.g., additionaland/or alternative LCP mapping restrictions as compared to the LCPmapping restrictions of Sections 38.321 and/or 38.331 of Release 15. Asillustrated in FIG. 5C, the first PDCP PDU 592 is sent to a first HARQentity 562 for a first component carrier (CC1) and the second PDCP PDU594 is sent to a second HARQ entity 564 for a second component carrier(CC2).

Referring to FIG. 5D, user plane stack includes a main stack 502 and asecondary stack 504. The main stack 502 corresponds to a first networkentity, such as a main base station, such as 105 a, and the secondarystack 504 corresponds to a secondary base station, such as 105 b. Themain stack 502 includes SDAP entity 512, a PDCP entity 522, a first RLCentity 532, and a first MAC entity 542. The secondary stack includes asecond RLC entity 534, and a second MAC entity 544. The MAC entities542, 544 may include a scheduler and/or a HARQ entity, similar to MACentity 542 of FIG. 5C, such as 552 and/or 562.

During operation, the SDAP entity 512 of the main stack 502 generates aPDCP SDU 580 and transmits the PDCP SDU 580 to the PDCP entity 522 ofthe main stack 502. The PDCP entity 522 generates a PDCP header 590 andcombines the PDCP header 590 and the PDCP SDU 580 to generate a firstPDCP PDU 592. The PDCP entity 522 duplicates the first PDCP PDU 592 togenerate the second PDCP PDU 594. The PDCP entity 522 transmits the twoPDCP PDUs 592, 594 to corresponding RLC entities 532, 534 of the mainstack 502 and secondary stack 504 respectively. The RLC entities 532,534 may perform RLC operations on the PDCP PDUs 592, 594, such as addcorresponding RLC headers. The RLC 532, 534 entities transport the PDCPPDUs 592, 594 (e.g., RLC modified PDCP PDUs) to corresponding MACentities 542, 544 of the main stack 502 and secondary stack 504respectively. Each of the MAC entities 542 and 544 (e.g., acorresponding scheduler 552 thereof) may perform MAC layer functions,such as LCP operations and LCP mappings as described with reference toFIG. 5C. An illustration of receiving uplink grants and transmission ofdata, such as PDCP PDU duplicated data, is illustrated in FIGS. 6A and6B.

Referring to FIGS. 6A and 6B, an example of PDCP PDU duplication isillustrated. FIG. 6A illustrates an example downlink operation and FIG.6B illustrates an example uplink operation. Referring to FIG. 6A, asystem 600 include a first transmission reception point (TRP) 605 a anda second TRP 605 b. As described above, the first TRP 605 a and thesecond TRP 605 b have spatial diversity (i.e., do not correspond to thesame antenna equipment) and may be incorporated in the same base station(same or different panel thereof) or in different base stations. Saidanother way, the UE 115 a may be operating in a carrier aggregationmulti-TRP mode or a dual connectivity multi-TRP mode.

In FIG. 6A, the UE 115 a receives a downlink message or messages (e.g.,one or more DCI, RRC, MAC CE, etc.) indicating uplink grants. The uplinkgrant or grants may include or correspond to dynamic grants, aconfigured grant, or multiple configured grants. When multiple downlinkmessages are used, the messages may be transmitted by the first TRP 605a, the second TRP 605 b, or both TRPs 605 a and 605 b.

The UE 115 a may perform the PDCP PDU duplication described withreference to FIGS. 5C and 5D, to generate first and second copies 692,694. Additionally, the UE 115 a performs the enhanced LCP mappingdescribed with reference to FIGS. 5C and 5D, to assign or map the firstcopy 692 to a first logical channel 615 a and the second copy 694 to asecond logical channel 615 b. In FIG. 6A, the UE 115 a may determinethat the first logical channel 615 a is restricted to send data to firstTRP 605 a (e.g., first TRP 605 a uplink grants) and that the secondlogical channel 615 b is restricted to send data to second TRP 605 b(e.g., TRP 605 b uplink grants).

Referring to FIG. 6B, the uplink transmission of the first and secondcopies 692 and 694 is depicted. In FIG. 6B, the UE 115 a transmits thefirst copy 692 to the first TRP 605 a using the uplink grant for thefirst TRP 605 a and transmits the second copy 694 to the second TRP 605b using the uplink grant for the second TRP 605 b. The UE 115 a maytransmit each copy 692, 694 with different transmission parameters, andthe transmission parameters may be suited for reception by eachcorresponding TRP. To illustrate, the transmission parameters (e.g.,transmission parameters which correspond to reception by the TRP) mayenable reception or enhanced reception by the corresponding TRP. Suchtransmission parameters include beam parameters, spatial filteringparameters, etc., or a combination thereof. Accordingly, the UE 115 acan transmit data (e.g., duplicated data) to two TRPs using the samecarrier (e.g., physical medium).

FIG. 7 illustrates an example of a wireless communications system 700that supports enhanced LCP mapping restrictions in accordance withaspects of the present disclosure. In some examples, wirelesscommunications system 700 may implement aspects of wirelesscommunication system 100. For example, wireless communications system700 may include network entity 705 (e.g., base station 105), UE 115, andoptionally second network entity 706 (e.g., second base station 105).Enhanced LCP mapping restrictions may enable reduced overhead andlatency when processing duplications and thus may increase throughputand reduce latency. Such increased throughput and reduced latency mayenable URLLC and may be utilized to increase reliability, and possiblythroughput when interference or blockage is present between a UE and aparticular TRP.

Network entity 705 and UE 115 may be configured to communicate viafrequency bands, such as FR1 having a frequency of 450 to 6000 MHz forSub-6 GHz or FR2 having a frequency of 24250 to 26000 MHz for mm-Wave.It is noted that sub-carrier spacing (SCS) may be equal to 15, 30, 60,or 120 kHz for some data channels. Network entity 705 and UE 115 may beconfigured to communicate via one or more component carriers (CCs), suchas representative first CC 781, second CC 782, third CC 783, and fourthCC 784. Although four CCs are shown, this is for illustration only, moreor fewer than four CCs may be used. One or more CCs may be used tocommunicate a Physical Downlink Control Channel (PDCCH), a PhysicalDownlink Shared Channel (PDSCH), a Physical Uplink Control Channel(PUCCH), or a Physical Uplink Shared Channel (PUSCH). In someimplementations, such transmissions may be scheduled by one or moreperiodic grants and may correspond to configured grants of the one ormore periodic grants.

Each periodic grant may have a corresponding configuration, such asconfiguration parameters/settings. The periodic grant configuration mayinclude configured grant (CG) configurations and settings. Additionally,or alternatively, one or more periodic grants (e.g., CGs thereof) mayhave or be assigned to a CC ID, such as intended CC ID.

Each CC may have a corresponding configuration, such as configurationparameters/settings. The configuration may include bandwidth, bandwidthpart, HARQ process, TCI state, RS, control channel resources, datachannel resources, or a combination thereof. Additionally, oralternatively, one or more CCs may have or be assigned to a Cell ID, aBandwidth Part (BWP) ID, or both. The Cell ID may include a unique cellID for the CC, a virtual Cell ID, or a particular Cell ID of aparticular CC of the plurality of CCs. Additionally, or alternatively,one or more CCs may have or be assigned to a HARQ ID. Each CC may alsohave corresponding management functionalities, such as, beam management,BWP switching functionality, or both.

In some implementations, two or more CCs are quasi co-located, such thatthe CCs have the same beam and/or same symbol. Additionally, oralternatively, CCs may be grouped as a set of one or more CCs, such as across carrier CORESET. Each CC in a CORESET may have the same cell ID,the same HARQ ID, or both.

In some implementations, control information may be communicated vianetwork entity 705 and UE 115. For example, the control information maybe communicated using MAC-CE transmissions, RRC transmissions, DCI,transmissions, another transmission, or a combination thereof.

UE 115 includes processor 702, memory 704, transmitter 710, receiver712, encoder, 713, decoder 714, combiner 715, and antennas 252 a-r.Processor 702 may be configured to execute instructions stored at memory704 to perform the operations described herein. In some implementations,processor 702 includes or corresponds to controller/processor 280, andmemory 704 includes or corresponds to memory 282. Memory 704 may also beconfigured to store LCP restriction data 706, SRS configurations 708,first transmission configurations 742, second transmissionconfigurations 744, or a combination thereof, as further describedherein.

The LCP restriction data 706 may include or correspond to one or moreLCP restrictions, such as LCP restrictions for multi-TRP modes. In aparticular implementations, the LCP restriction data 706 include SRSconfigurations 708. The LCP restriction data 706 may be transmitted byMAC-CE, DCI, or RRC message. The SRS configurations may include a set ofall enabled or allowed SRS configurations for a particular logicalchannel, for multiple logical channels, or for all logical channels. Ina particular implementation, the SRS configurations include a set ofenabled or allowed SRS configurations for one or more logical channels.An SRS configuration for a particular transmission or transmissions maybe indicated in an uplink grant.

Each uplink grant configuration may have a corresponding transmissionconfiguration and/or transmission parameters. As illustrated in FIG. 7 ,UE 115 stores a first transmission configuration 742 and a secondtransmission configuration 744. The first transmission configuration 742may include or correspond to first transmission parameters for (e.g.,suited for reception by) a first TRP and the second transmissionconfiguration 744 may include or correspond to second transmissionparameters for (e.g., suited for reception by) a first TRP. Toillustrate, the transmission parameters may include schedulinginformation such as when and where to send. As another illustration, thetransmission parameters may include the transmission and/or receptioncharacteristics for transmitting/receiving, such as BWP ID, beam sweepenabled, beam sweep pattern, etc., i.e., how to send.

Transmitter 710 is configured to transmit data to one or more otherdevices, and receiver 712 is configured to receive data from one or moreother devices. For example, transmitter 710 may transmit data, andreceiver 712 may receive data, via a network, such as a wired network, awireless network, or a combination thereof. For example, UE 115 may beconfigured to transmit and/or receive data via a direct device-to-deviceconnection, a local area network (LAN), a wide area network (WAN), amodem-to-modem connection, the Internet, intranet, extranet, cabletransmission system, cellular communication network, any combination ofthe above, or any other communications network now known or laterdeveloped within which permits two or more electronic devices tocommunicate. In some implementations, transmitter 710 and receiver 712may be replaced with a transceiver. Additionally, or alternatively,transmitter 710, receiver, 712, or both may include or correspond to oneor more components of UE 115 described with reference to FIG. 2 .

Encoder 713 and decoder 714 may be configured to encode and decode, suchas jointly encode and jointly decode, respectively. Duplicator 715 maybe configured to duplicate data, such as PDCP PDUs, for encoding byencoder 713. LCH Prioritizer 716 may be configured to select a logicalchannel based on LCP mapping restrictions and/or rules (e.g., LCPlogic).

Network entity 705 includes processor 730, memory 732, transmitter 734,receiver 736, encoder 737, decoder 738, combiner 739, and antennas 234a-t. Processor 730 may be configured to execute instructions stores atmemory 732 to perform the operations described herein. In someimplementations, processor 730 includes or corresponds tocontroller/processor 240, and memory 732 includes or corresponds tomemory 242. Memory 732 may be configured to store LCP restriction data706, SRS configurations 708, first transmission configurations 742,second transmission configurations 744, or a combination thereof,similar to the UE 115 and as further described herein.

Transmitter 734 is configured to transmit data to one or more otherdevices, and receiver 736 is configured to receive data from one or moreother devices. For example, transmitter 734 may transmit data, andreceiver 736 may receive data, via a network, such as a wired network, awireless network, or a combination thereof. For example, network entity705 may be configured to transmit and/or receive data via a directdevice-to-device connection, a local area network (LAN), a wide areanetwork (WAN), a modem-to-modem connection, the Internet, intranet,extranet, cable transmission system, cellular communication network, anycombination of the above, or any other communications network now knownor later developed within which permits two or more electronic devicesto communicate. In some implementations, transmitter 734 and receiver736 may be replaced with a transceiver. Additionally, or alternatively,transmitter 734, receiver, 736, or both may include or correspond to oneor more components of network entity 705 described with reference toFIG. 2 . Encoder 737, decoder 738, and combiner 739 may include the samefunctionality as described with reference to encoder 713, and decoder714, respectively.

During operation of wireless communications system 700, network entity705 may determine that UE 115 has enhanced LCP mapping restrictioncapability, such as SRS based LCP mapping. For example, UE 115 maytransmit a message 748 that includes an enhanced LCP mapping restrictioncapability indicator 792. Indicator 792 may indicate enhanced LCPmapping capability or a particular type of enhanced LCP mappingcapability, such as enhanced LCP mapping for duplications, for multi-TRPmodes, or with a particular type of LCP restriction (e.g., SRS). In someimplementations, network entity 705 sends control information toindicate to UE 115 that enhanced LCP mapping restriction is to be used.For example, in some implementations, message 748 (or another message,such as response or trigger message) is transmitted by the networkentity 705.

Network entity 705 transmits LCP configuration transmission 750 (e.g., aRRC or MAC CE) to UE 115. LCP configuration transmission 750 includesLCP restriction data 706, such as an enhanced LCP mapping restriction.In a particular implementation, the LCP restriction data include orcorresponds to a set of enabled or allowed SRS configurations for alogical channel or channels. UE 115 receives the LCP configurationtransmission 750 and updates its stored LCP restriction data 706 basedon the LCP restriction data 706 of LCP configuration transmission 750.

After transmission of the message 748 (e.g., a configuration message,such as a RRC message or a MAC CE) and/or LCP configuration transmission750, transmissions may be scheduled by the network entity 705, the UE115, or both. Such scheduled transmissions may include shared channeltransmissions, such as PUSCH transmissions. These scheduledtransmissions may include or correspond to dynamic or periodicallyscheduled uplink transmissions. A dynamic grant may schedule a singleuplink grant or uplink grant instance, and a periodic grant may schedulea single configured grant and multiple uplink grant instances. Theuplink grants may include or correspond to DCI, RRC, or MAC CE.

In the example of FIG. 7 , network entity 705 transmits a first downlinktransmission 752 to UE 115. The first downlink transmission 752 includesa logical channel indicator and/or transmission indicator, such as afirst particular SRS configuration 708 a for a corresponding uplinkgrant or uplink grant instance. The uplink grant may include orcorrespond to a particular TRP. UE 115 determines a logical channelbased at least on the first particular SRS configuration 708 a and theupdated LCP restriction data 706. For example, LCP Prioritizer 716performs LCP mapping operations and determines the logical channel for afirst uplink transmission 754 based at least on the first particular SRSconfiguration 708 a and the updated LCP restriction data 706. In someimplementations, UE 115 determines a second logical channel based atleast on a second particular SRS configuration 708 b (included in 752)and the updated LCP restriction data 706. For example, in suchimplementations first downlink transmission 752 includes two uplinkgrants and LCP Prioritizer 716 performs LCP mapping operations anddetermines the second logical channel for a second uplink transmission764 corresponding to a second TRP based at least on the secondparticular SRS configuration 708 b and the updated LCP restriction data706.

Network entity 705 may transmit a second downlink transmission 762 to UE115 in other implementations; the second downlink transmission 762includes a second particular SRS configuration 708 b for a second uplinkgrant associated with a second TRP. In such implementations, UE 115determines a second logical channel based at least on the secondparticular SRS configuration 708 b (included in 762) and the updated LCPrestriction data 706. For example, LCP Prioritizer 716 performs LCPmapping operations and determines the second logical channel for thesecond uplink transmission 764 based at least on the second particularSRS configuration 708 b and the updated LCP restriction data 706.

After the UE 115 performs logical channel prioritization operations todetermine logical channels for the uplink grants, the UE 115 schedulesthe transmissions. In the example of FIG. 7 , the UE 115 schedules thefirst uplink transmission 754 and the second uplink transmission 764using the first and second logical channels respectively. The UE 115 maytransmit the transmissions 754, 764 via the same carrier. For example,the UE 115 may transmit the transmissions 754, 764 on the same carrierusing different transmission configurations 742, 744 which are suitedfor reception by correspond TRPs. Thus, the UE 115 may transmit thetransmissions 754, 764 via the same carrier (e.g., simultaneously orconcurrently, such as partially concurrently) to two different TRPs,even when duplicated data is being transmitted. In some implementations,UE 115 duplicates at least a portion of transmissions 754, 764. Forexample, UE 115 may perform PDCP PDU duplication as described in FIGS.5C and 5D.

Thus, FIG. 7 describes enhanced LCP mapping restrictions for a UE. Usingenhanced LCP mapping may enable improvement in multi-TRP modes and/orwhen duplicating data for transmission. Performing LCP operations withenhanced LCP mapping restrictions enables a network to reduce latencyand improve reliability. Improving performance may improve throughputfor communications on the network and enable use of mm wave frequencyranges and URLLC modes.

Referring to FIGS. 8A-8F, examples of messages and fields which mayinclude an LCP configuration are illustrated. FIG. 8A is an example of ablock diagram of an exemplary field layout of a downlink controlmessage. FIGS. 8B-8F are examples of different configurations of aparticular field of the downlink control message of FIG. 8A.

Referring to FIG. 8A, an example of a field layout of a downlink controlmessage 800 is illustrated. The downlink control message 800 may includeor correspond to a downlink transmission (e.g., 752 and/or 762) of FIG.7 . The downlink control message 800 includes one or more fields. Asillustrated in FIG. 8A, the downlink control message 800 is a DCI. A DCI(or DCI message) may have multiple different types or formats, such asFormat 0_0, 0_1, 1_0, 1_1, etc. In the example illustrated in FIG. 8A,the downlink control message 800 includes one or more first fields 812,a value field 814, and one or more second fields 816. Although threefields are illustrated in FIG. 8A, DCI 800 may include more than threefields or fewer than three fields.

The value field 814 may indicate a value for SRI, a value for SSB(Synchronization Signal Block), a value for RS (e.g., NZP-CSI-RS), avalue for TCI state, or a combination thereof, for a correspondingtransmission. For example, the value field 814 indicates values for SRIand RV for a corresponding transmission. The value indicated by thevalue field 814 may be used for LCP, such as for enhanced LCPrestrictions. In a particular implementation, the value field 814 is amulti-bit field. In the implementations described herein, the values (ora sequence thereof) of the value field 814 for the transmission can berepurposed to identify values for a different parameter, as illustratedin FIGS. 8B-8F. Additionally or alternatively, value field 814 may be afirst field or a last field. Although fields are described in FIG. 8A,the value us

Referring to FIGS. 8B-8F, examples of value fields 814 are illustrated.In FIGS. 8B-8F, the value field 814 includes or corresponds to an SRIfield 820, and may indicate a value for SRI, a value for SRS, a valuefor SSB, a value for RS, a value for TCI state, or a combination thereoffor a corresponding transmission. In FIG. 8B, the SRI field 820indicates a value for SRI for a corresponding transmission, SRI value832. In a particular implementation, the SRI field 820 is a multi-bitfield. In the implementations described herein, the values (or asequence thereof) of the SRI field 820 can be repurposed to identifyvalues for other parameters, as illustrated in FIGS. 8C-8F.

In FIG. 8C, an SRI field 822 includes or indicates an SSB value 834. InFIG. 8D, an SRI field 824 includes or indicates an NZP-CSI-RS value 836.In FIG. 8E, an SRI field 826 includes or indicates an SSB value 834,which indicates a TCI value 842, such as a TCI state value. In FIG. 8F,an SRI field 828 includes or indicates an NZP-CSI-RS value 836, whichindicates a TCI value 842, such as a TCI state value.

The SRI field (e.g., 822-828) may indicate a value, such as a value(s)for the SRS, directly. For example, a value of the SRI field, i.e., avalue identified by bits thereof, is or indicates the value for one ormore of the SRI values for the corresponding transmission(s). Toillustrate, a bit of the SRI field Corresponds to a SRI value for aparticular transmission.

Alternatively, the SRI field may indicate a value indirectly, i.e.,identify the value by indicating a member of set. For example, a valueof the SRI field, i.e., a value identified by bits thereof, indicates aparticular member of a set of values, and a value (e.g., a second value)of the particular member indicates the parameter value. To illustrate, abit sequence of 111 illustrates an 8^(th) member of a set. Although, aDCI implementation is illustrated in FIGS. 8A-8F, the downlink controlmessage 800 may be a MAC CE or an RRC message. In such implementations,the downlink control message 800 may include an SRI field in thealternative to the SRI field.

FIG. 9 is a block diagram illustrating example blocks executed by a UEconfigured according to an aspect of the present disclosure. The exampleblocks will also be described with respect to UE 115 as illustrated inFIG. 11 . FIG. 11 is a block diagram illustrating UE 115 configuredaccording to one aspect of the present disclosure. UE 115 includes thestructure, hardware, and components as illustrated for UE 115 of FIG. 2. For example, UE 115 includes controller/processor 280, which operatesto execute logic or computer instructions stored in memory 282, as wellas controlling the components of UE 115 that provide the features andfunctionality of UE 115. UE 115, under control of controller/processor280, transmits and receives signals via wireless radios 1100 a-r andantennas 252 a-r. Wireless radios 1100 a-r includes various componentsand hardware, as illustrated in FIG. 2 for UE 115, includingmodulator/demodulators 254 a-r, MIMO detector 256, receive processor258, transmit processor 264, and TX MIMO processor 266. As illustratedin the example of FIG. 11 , memory 282 stores Multi-TRP logic 1102, LCPlogic 1103, duplication logic 1104, LCP restrictions data 1105, SRSconfigurations data 1106 (e.g., allowed SRS configurations), SRSconfiguration data 1107, logical channel data 1108, and transportchannels data 1109, and transmission parameter data 1110.

At block 900, a mobile communication device, such as a UE, receives alogical channel prioritization (LCP) restriction configuration for alogical channel indicating a set of SRS configurations. A UE, such as UE115, receives a downlink transmission (e.g., first downlinktransmission, such as a DCI, RRC, MAC CE) via wireless radios 1100 a-rand antennas 252 a-r. The downlink transmission (e.g., 750) includes aLCP restriction (e.g., 706) for at least one logical channel. The LCPrestriction may be SRS/SRI based, such as may indicate a set ofallowable SRS/SRI configurations (e.g., 708).

The UE 115 may execute, under control of controller/processor 280,Multi-TRP logic 1102, stored in memory 282. The execution environment ofMulti-TRP logic 1102 provides the functionality for UE 115 to define andperform the Multi-TRP procedures. Additionally, the UE 115 may executeone or more of LCP logic 1103 and or duplication logic 1104. Theexecution environment of Multi-TRP logic 1102 (and optionally LCP logic1103 and/or duplication logic 1104) defines the different Multi-TRPprocesses, such as determining a Multi-TRP mode, determining an LCPmode, determining enhanced LCP restrictions, updating LCP restrictions,selecting a logical channel, duplicating data, etc. To illustrate, UE115 may store/update LCP restrictions data 1105 based on the receivedLCP restriction and/or may store/update the allowed SRS configurations1106 based on the received set of allowable SRS/SRI configurations.Additionally, UE 115 may send an acknowledgement message responsive tothe downlink transmission to indicate successful reception and decodingof the downlink transmission.

At block 901, the UE 115 receives an uplink grant indicating an uplinkgrant instance and an SRS configuration for the uplink grant instance.The UE 115 receives an uplink grant (e.g., second downlink transmission)via wireless radios 1100 a-r and antennas 252 a-r. The uplink grant mayindicate or include one or more uplink grant instances for a particularTRP, and may indicate a corresponding SRS configuration 1107 (e.g., 708a, 708 b) for the uplink grant instance(s) and the particular TRP.

In some implementations, the uplink grant is a periodic grant. In otherimplementations, another uplink grant is received that includes or is aperiodic grant. In such periodic grant implementations, the UE 115, mayexecute, under control of controller/processor 280, periodic grantlogic, stored in memory 282. The execution environment of the periodicgrant logic defines the different periodic grant processes, such asdetermining a periodic grant configuration, configured grantconfigurations and/or scheduling uplink grants. The UE 115 may scheduleor determine a schedule for an upcoming uplink transmission based on theperiodic grant, and may transmit such downlink transmissions usingantennas 252 a-r and wireless radios 1100 a-r.

At block 902, the UE 115 selects the logical channel to use resources ofthe uplink grant instance based in part on the set of SRS configurationsand the SRS configuration for the uplink grant instance. The UE 115selects a logical channel from a plurality of logical channels based onthe enhanced LCP mapping restrictions and the indication in the uplinkgrant (e.g., SRS/SRI based indication). For example, the executionenvironment of the Multi-TRP logic 1102 (and optionally LCP logic 1103and/or duplication logic 1104) provides UE 115 the functionalitiesdescribed with respect to the various aspects of the present disclosure,such as performing LCP operations. To illustrate, within the executionenvironment of Multi-TRP logic 1102 (and optionally LCP logic 1103), UE115, under control of controller/processor 280, may determine aparticular logical channel of the logical channels indicated by logicalchannel data 1108 based on LCP restrictions 1105, SRS configurations1106, and SRS configuration 1107.

As an illustrative example, UE 115 selects the logical channel bydetermining the SRS configuration of the uplink grant instance based ona value of an SRS resource indicator field associated with the uplinkgrant instance, and determining the logical channel to use the resourcesof the uplink grant instance based on the value of the SRS resourceindicator field associated with the uplink grant instance. As anotherillustrative example, UE 115 determines possible logical channels of aplurality of logical channels for the uplink grant instance bydetermining useable logical channels of the plurality of logicalchannels for the uplink grant instance based on a corresponding set ofSRS configurations associated with each logical channel of the pluralityof logical channels, and the plurality of logical channels including thelogical channel, determining non-useable logical channels of theplurality of logical channels for the uplink grant instance based on LCPmapping restrictions (e.g., generic or conventional LCP mappingsrestrictions, such as non SRS/SRI LCP mapping restrictions, or both.

The UE 115 may execute additional blocks (or the UE 115 may beconfigured further perform additional operations) in otherimplementations. For example, the UE 115 may transmit data of theselected logical channel, send an acknowledgment for the uplink grant,or a combination thereof, after block 902. As another example, the UE115 may duplicate the data of the selected logical channel to generatesecond data, perform second LCP mapping for the second data to determinea second logical channel, and transmit the second data of the secondlogical channel. In a particular implementation, that data is sent to afirst TRP and the duplicated data is sent to a second TRP using the samecarrier, as described with reference to FIGS. 5C, 5D, and 6B. As anadditional example, the UE 115 may perform one or more operationsdescribed above. As yet another example, the UE 115 may perform one ormore aspects as described below.

In a first aspect, the UE 115 transmits data via the selected logicalchannel, where the set of SRS configurations associated with the logicalchannel is a subset of a set of allowed SRS configurations for aplurality of logical channels including the logical channel.

In a second aspect, alone or in combination with one or more of theabove aspects, selecting the logical channel to use resources of theuplink grant instance based in part on the set of SRS configurations andthe SRS configuration includes: the UE 115 determining the SRSconfiguration for the uplink grant instance based on a value of an SRSresource indicator field associated with the uplink grant instance, anddetermining the logical channel to use the resources of the uplink grantinstance based on the value of the SRS resource indicator fieldassociated with the uplink grant instance.

In a third aspect, alone or in combination with one or more of the aboveaspects, determining the logical channel to use resources of the uplinkgrant instance based on the value of the SRS resource indicator fieldincludes: the UE 115 determining possible logical channels of aplurality of logical channels for the uplink grant instance based on LCPmapping restrictions, and determining the logical channel to useresources of the uplink grant instance from the possible logicalchannels based on the value of the SRS resource indicator field.

In a fourth aspect, alone or in combination with one or more of theabove aspects, determining possible logical channels of a plurality oflogical channels for the uplink grant instance includes: the UE 115determining useable logical channels of the plurality of logicalchannels for the uplink grant instance based on a corresponding set ofSRS configurations associated with each logical channel of the pluralityof logical channels, and the plurality of logical channels including thelogical channel; determining non-useable logical channels of theplurality of logical channels for the uplink grant instance based on LCPmapping restrictions; or both.

In a fifth aspect, alone or in combination with one or more of the aboveaspects, the UE 115 transmits data via the selected logical channel,wherein the set of SRS configurations associated with the logicalchannel is a subset of a set of allowed SRS configurations for aplurality of logical channels including the logical channel, duplicatesa PDCP PDU to generate a second PDCP PDU, wherein the PDCP PDUcorresponds to the data transmitted via the selected logical channel;receives a second uplink grant indicating a second uplink grant instanceand a second SRS configuration for the second uplink grant instance;selects a second logical channel to use resources of the second uplinkgrant instance based on the set of allowed SRS configurations and thesecond SRS configuration, and transmits second data via the selectedsecond logical channel, the second data including the second PDCP PDU.

In a sixth aspect, alone or in combination with one or more of the aboveaspects, the uplink grant further indicates a second uplink grantinstance, and the UE 115 further transmits data via the selected logicalchannel, wherein the set of SRS configurations associated with thelogical channel is a subset of a set of allowed SRS configurations for aplurality of logical channels including the logical channel, duplicatesa PDCP PDU to generate a second PDCP PDU, wherein the PDCP PDUcorresponds to the data transmitted via the selected logical channel,selects a second logical channel to use resources of the second uplinkgrant instance based on the set of allowed SRS configurations and asecond SRS configuration for the second uplink grant instance, andtransmits second data via the selected logical channel, the second dataincluding the second PDCP PDU.

In a seventh aspect, alone or in combination with one or more of theabove aspects, the SRS configuration for the uplink grant instanceindicates a SRS indicator value.

In an eighth aspect, alone or in combination with one or more of theabove aspects, the SRS configuration for the uplink grant instanceindicates an SSB value.

In a ninth aspect, alone or in combination with one or more of the aboveaspects, the SRS configuration for the uplink grant instance indicatesan NZP-CSI-RS-Resource value.

In a tenth aspect, alone or in combination with one or more of the aboveaspects, the SRS configuration indicates a TCI indication, and whereinthe TCI indication comprises a TCI state indication of a SSB or aNZP-CSI-RS-Resource.

In an eleventh aspect, alone or in combination with one or more of theabove aspects, the LCP restriction configuration is included in a DCI, aMAC CE, or an RRC message.

In a thirteenth aspect, alone or in combination with one or more of theabove aspects, the uplink grant comprises a dynamic grant, and whereinthe uplink grant comprises a DCI.

In a fourteenth aspect, alone or in combination with one or more of theabove aspects, the uplink grant comprises a configured grant, andwherein the uplink grant comprises one or more of a DCI or an RRCmessage.

In a fifteenth aspect, alone or in combination with one or more of theabove aspects, the UE 115 transmits a message including an SRS signal,wherein an SRI field of the LCP restriction configuration is generatedbased on the SRS signal.

Accordingly, a UE and a base station may perform enhanced LCP mappingfor Multi-TRP modes. By performing enhanced LCP mapping for Multi-TRPs,additional functionality can be achieved, such as duplicated data can besent to two different TRPs using the same carrier. Consequently, latencyand overhead may be reduced and throughput and reliability may beincreased.

FIG. 10 is a block diagram illustrating example blocks executed by abase station configured according to an aspect of the presentdisclosure. The example blocks will also be described with respect togNB 105 (or eNB) as illustrated in FIG. 12 . FIG. 12 is a block diagramillustrating gNB 105 configured according to one aspect of the presentdisclosure. The gNB 105 includes the structure, hardware, and componentsas illustrated for gNB 105 of FIG. 2 . For example, gNB 105 includescontroller/processor 240, which operates to execute logic or computerinstructions stored in memory 242, as well as controlling the componentsof gNB 105 that provide the features and functionality of gNB 105. ThegNB 105, under control of controller/processor 240, transmits andreceives signals via wireless radios 1200 a-t and antennas 234 a-r.Wireless radios 1200 a-t includes various components and hardware, asillustrated in FIG. 2 for gNB 105, including modulator/demodulators 232a-t, MIMO detector 236, receive processor 238, transmit processor 220,and TX MIMO processor 230. The data 1202-1207 in memory 242 may includeor correspond to the corresponding data 1102-1110 in memory 282,respectively.

At block 1000, a network entity, such as a gNB, transmits a logicalchannel prioritization (LCP) restriction configuration for a logicalchannel indicating a set of SRS configurations. A gNB, such as gNB 105,may execute, under control of controller/processor 240, Multi-TRP logic1202, stored in memory 242. The execution environment of Multi-TRP logic1202 provides the functionality for gNB 105 to define and perform theMulti-TRP procedures.

The execution environment of Multi-TRP logic 1202 defines the differentMulti-TRP processes, such as signaling for enhanced LCP mappingoperations and indicating LCP restriction configurations. To illustrate,the gNB 105 transmits a downlink configuration message (e.g., 750)including 1204 and 1205 to the UE 115 via wireless radios 1200 a-t andantennas 234 a-r, such as responsive to a configuration, capabilities,or mode message (e.g., 748).

At block 1001, the gNB 105 determines data of a logical channel of aparticular user device is to be scheduled. The execution environment ofMulti-TRP logic 1202 provides the functionality for gNB 105 to defineand perform the Multi-TRP procedures. Within the execution environmentof the Multi-TRP logic 1202, gNB 105, under control ofcontroller/processor 240, determines that the UE has data of a logicalchannel to be scheduled. The gNB 105 may determine that the UE has datato send responsive to receiving an uplink message. When the UE issending data via configured grants, the gNB 105 may determine that theUE has and will have data to transmit periodically in the future.

At block 1002, the gNB 105 transmits an uplink grant indicating anuplink grant instance for the particular user device indicating an SRSconfiguration of the set of SRS configurations associated with thelogical channel. The gNB 105 generates and transmits a downlinktransmission (e.g., second downlink transmission) via antennas 234 a-tand wireless radios 1200 a-t. The downlink transmission may include orcorrespond to one of the downlink transmissions of FIG. 6A or 7 , suchas 752, 762. For example, the downlink transmission may include an SRSconfiguration 1206 (e.g., 708 a, 708 b, or both).

For example, the execution environment of Multi-TRP logic 1202 (andoptionally LCP logic 1203) defines the different Multi-TRP (and LCP)processes, such as LCP restrictions and configurations. As gNB 105, Toillustrate, within the execution environment gNB 105, under control ofcontroller/processor 240, selects an SRS configuration 1206 from allowedSRS configurations 1205 and generates (e.g., encodes) the downlinktransmissions (e.g., DCI or RRC) which includes the SRS configuration1206.

At block 1003, the gNB 105 receives a transmission corresponding to theuplink grant instance and including the data of the logical channel. ThegNB receives an uplink transmission via antennas 234 a-t and wirelessradios 1200 a-t. The uplink transmission (e.g., 754, 764) may beconfigured for reception by the gNB 105 based on the SRS configuration1206 and the LCP restrictions 1204 and allowed SRS configurations 1205.To illustrate, the uplink transmission may be associated with or sentvia transmission parameters 1110 and/or 1207.

The gNB 105 (or another base station or network entity) may executeadditional blocks (or the gNB 105 may be configured further performadditional operations) in other implementations. For example, the gNB105 may perform one or more operations described above. As yet anotherexample, the gNB 105 may perform one or more aspects as described below.

In a first aspect, the gNB 105 transmits a second LCP restrictionconfiguration for a second logical channel indicating a second set ofSRS configurations associated with the second logical channel,determines that second data of the second logical channel of theparticular UE is to be scheduled, transmits a second uplink grantindicating a second uplink grant instance for the particular UE, whereinthe second uplink grant instance indicates a second SRS configuration ofthe second set of SRS configurations associated with the second logicalchannel, receives a second transmission corresponding to the seconduplink grant instance including the second data of the second logicalchannel.

In a second aspect, alone or in combination with one or more of theabove aspects, the LCP restriction configuration and the second LCPrestriction configuration are transmitted separately.

In a third aspect, alone or in combination with one or more of the aboveaspects, the LCP restriction configuration and the second LCPrestriction configuration are transmitted in the same transmission.

In a fourth aspect, alone or in combination with one or more of theabove aspects, a first transmission reception point receives thetransmission and a second transmission reception point receives thesecond transmission, and wherein the transmission and the secondtransmission include duplicated data.

In a fifth aspect, alone or in combination with one or more of the aboveaspects, a first base station receives the transmission and a secondbase station receives the second transmission, and wherein thetransmission and the second transmission include duplicated data.

In a sixth aspect, alone or in combination with one or more of the aboveaspects, the SRS configuration is indicated by an SRS indicator fieldwhich indicates a SRS indicator value.

In a seventh aspect, alone or in combination with one or more of theabove aspects, the SRS configuration is indicated by an SRS indicatorfield which indicates an SSB value.

In an eighth aspect, alone or in combination with one or more of theabove aspects, the SRS configuration is indicated by an SRS indicatorfield which indicates an NZP-CSI-RS-Resource value.

In a ninth aspect, alone or in combination with one or more of the aboveaspects, the SRS configuration is indicated by an SRS indicator fieldwhich indicates a TCI indication, and wherein the TCI indicationcomprises a TCI state indication of a SSB or a NZP-CSI-RS-Resource.

In a tenth aspect, alone or in combination with one or more of the aboveaspects, the LCP restriction configuration is included in a DCI, a MACCE, or an RRC message.

In an eleventh aspect, alone or in combination with one or more of theabove aspects, the uplink grant comprises a dynamic grant or aconfigured grant.

In a twelfth aspect, alone or in combination with one or more of theabove aspects, prior to transmitting the LCP restriction configuration:the gNB 105 receives a message including an SRS signal from the UE, andgenerates an SRI field of the LCP restriction configuration based on theSRS signal.

Accordingly, a UE and a base station may perform enhanced LCP mappingfor Multi-TRP modes. By performing enhanced LCP mapping for Multi-TRPs,additional functionality can be achieved, such as duplicated data can besent to two different TRPs using the same carrier. Consequently, latencyand overhead may be reduced and throughput and reliability may beincreased.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

The functional blocks and modules in FIGS. 9 and 10 may compriseprocessors, electronics devices, hardware devices, electronicscomponents, logical circuits, memories, software codes, firmware codes,etc., or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the disclosure herein may be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure. Skilled artisans will also readilyrecognize that the order or combination of components, methods, orinteractions that are described herein are merely examples and that thecomponents, methods, or interactions of the various aspects of thepresent disclosure may be combined or performed in ways other than thoseillustrated and described herein.

The various illustrative logical blocks, modules, and circuits describedin connection with the disclosure herein may be implemented or performedwith a general-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with thedisclosure herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In one or more exemplary designs, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another.Computer-readable storage media may be any available media that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, such computer-readable media can compriseRAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other medium that canbe used to carry or store desired program code means in the form ofinstructions or data structures and that can be accessed by ageneral-purpose or special-purpose computer, or a general-purpose orspecial-purpose processor. Also, a connection may be properly termed acomputer-readable medium. For example, if the software is transmittedfrom a website, server, or other remote source using a coaxial cable,fiber optic cable, twisted pair, or digital subscriber line (DSL), thenthe coaxial cable, fiber optic cable, twisted pair, or DSL, are includedin the definition of medium. Disk and disc, as used herein, includescompact disc (CD), laser disc, optical disc, digital versatile disc(DVD), floppy disk and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

As used herein, including in the claims, the term “and/or,” when used ina list of two or more items, means that any one of the listed items canbe employed by itself, or any combination of two or more of the listeditems can be employed. For example, if a composition is described ascontaining components A, B, and/or C, the composition can contain Aalone; B alone; C alone; A and B in combination; A and C in combination;B and C in combination; or A, B, and C in combination. Also, as usedherein, including in the claims, “or” as used in a list of itemsprefaced by “at least one of” indicates a disjunctive list such that,for example, a list of “at least one of A, B, or C” means A or B or C orAB or AC or BC or ABC (i.e., A and B and C) or any of these in anycombination thereof.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein.

What is claimed is:
 1. A method of wireless communication comprising:receiving, by a user equipment (UE), a logical channel prioritization(LCP) restriction configuration for a logical channel indicating a setof Sounding Reference Signal (SRS) configurations associated with thelogical channel; receiving, by the UE, an uplink grant indicating anuplink grant instance and an SRS configuration for the uplink grantinstance; selecting, by the UE, the logical channel to use resources ofthe uplink grant instance based in part on the set of SRS configurationsand the SRS configuration for the uplink grant instance; transmitting,by the UE, data via the selected logical channel, wherein the set of SRSconfigurations associated with the logical channel is a subset of a setof allowed SRS configurations for a plurality of logical channelsincluding the logical channel; and transmitting, by the UE, second datavia a second logical channel based on the set of allowed SRSconfigurations, the second data including a second Packet DataConvergence Protocol (PDCP) Packet Data Unit (PDU), the second PDCP PDUgenerated based on duplicating a PDCP PDU corresponding to the datatransmitted via the selected logical channel.
 2. The method of claim 1,wherein selecting, by the UE, the logical channel to use resources ofthe uplink grant instance based in part on the set of SRS configurationsand the SRS configuration includes: determining the SRS configurationfor the uplink grant instance based on a value of an SRS resourceindicator field associated with the uplink grant instance; anddetermining the logical channel to use the resources of the uplink grantinstance based on the value of the SRS resource indicator fieldassociated with the uplink grant instance.
 3. The method of claim 2,wherein determining the logical channel to use resources of the uplinkgrant instance based on the value of the SRS resource indicator fieldincludes: determining possible logical channels of a plurality oflogical channels for the uplink grant instance based on LCP mappingrestrictions; and determining the logical channel to use resources ofthe uplink grant instance from the possible logical channels based onthe value of the SRS resource indicator field.
 4. The method of claim 3,wherein determining possible logical channels of a plurality of logicalchannels for the uplink grant instance includes: determining useablelogical channels of the plurality of logical channels for the uplinkgrant instance based on a corresponding set of SRS configurationsassociated with each logical channel of the plurality of logicalchannels, and the plurality of logical channels including the logicalchannel; determining non-useable logical channels of the plurality oflogical channels for the uplink grant instance based on LCP mappingrestrictions; or both.
 5. The method of claim 1, further comprising:receiving, by the UE, a second uplink grant indicating a second uplinkgrant instance and a second SRS configuration for the second uplinkgrant instance; selecting, by the UE, the second logical channel to useresources of the second uplink grant instance based on the set ofallowed SRS configurations and the second SRS configuration; and.
 6. Themethod of claim 1, wherein the uplink grant further indicates a seconduplink grant instance, and further comprising: selecting, by the UE, thesecond logical channel to use resources of the second uplink grantinstance based on the set of allowed SRS configurations and a second SRSconfiguration for the second uplink grant instance.
 7. The method ofclaim 1, further comprising: selecting, by the UE, the second logicalchannel based on the set of allowed SRS configurations and a second SRSconfiguration.
 8. The method of claim 1, further comprising:duplicating, by the UE, the PDCP PDU to generate the second PDCP PDU. 9.The method of claim 1, further comprising: determining, by the UE, theSRS configuration for the uplink grant instance based on a value of anSRS resource indicator field associated with the uplink grant instance.10. The method of claim 1, wherein the set of SRS configurations includea set of allowed SRS configurations for the logical channel.
 11. Themethod of claim 1, wherein the data is transmitted based receiving onthe uplink grant.
 12. An apparatus configured for wirelesscommunication, the apparatus comprising: at least one processor; and amemory coupled to the at least one processor, wherein the at least oneprocessor is configured: to receive, by a user equipment (UE), a logicalchannel prioritization (LCP) restriction configuration for a logicalchannel indicating a set of Sounding Reference Signal (SRS)configurations associated with the logical channel; to receive, by theUE, an uplink grant indicating an uplink grant instance and an SRSconfiguration for the uplink grant instance; and to select, by the UE,the logical channel to use resources of the uplink grant instance basedin part on the set of SRS configurations and the SRS configuration forthe uplink grant instance; transmitting, by the UE, data via theselected logical channel, wherein the set of SRS configurationsassociated with the logical channel is a subset of a set of allowed SRSconfigurations for a plurality of logical channels including the logicalchannel; and transmitting, by the UE, second data via a second logicalchannel based on the set of allowed SRS configurations, the second dataincluding a second Packet Data Convergence Protocol (PDCP) Packet DataUnit (PDU), the second PDCP PDU generated based on duplicating a PDCPPDU corresponding to the data transmitted via the selected logicalchannel.
 13. The apparatus of claim 12, wherein the SRS configurationfor the uplink grant instance indicates a SRS indicator value.
 14. Theapparatus of claim 12, wherein the SRS configuration for the uplinkgrant instance indicates an synchronization signal block (SSB) value.15. The apparatus of claim 12, wherein the SRS configuration for theuplink grant instance indicates an non-zero power channel stateinformation reference signal resource (NZP-CSI-RS-Resource) value. 16.The apparatus of claim 12, wherein the SRS configuration indicates atransmission configuration indicator (TCI) indication, and wherein theTCI indication comprises a TCI state indication of a SSB or aNZP-CSI-RS-Resource.
 17. The apparatus of claim 12, wherein the LCPrestriction configuration is included in downlink control information(DCI), a medium access control element (MAC CE), or an radio resourcecontrol (RRC) message.
 18. The apparatus of claim 12, wherein the uplinkgrant comprises a dynamic grant, and wherein the uplink grant comprisesdownlink control information (DCI).
 19. The apparatus of claim 12,wherein the uplink grant comprises a configured grant, and wherein theuplink grant comprises one or more of downlink control information (DCI)or an radio resource control (RRC) message.
 20. The apparatus of claim12, wherein the processor is further configured to: transmit, by the UE,a message including an SRS signal, wherein an SRS resource indicator(SRI) field of the LCP restriction configuration is generated based onthe SRS signal.
 21. The apparatus of claim 12, wherein the at least oneprocessor is further configured: to select, by the UE, the secondlogical channel based on the set of allowed SRS configurations and asecond SRS configuration.
 22. The apparatus of claim 12, wherein the atleast one processor is further configured: to duplicate, by the UE, thePDCP PDU to generate the second PDCP PDU.
 23. The apparatus of claim 12,wherein the at least one processor is further configured: to determine,by the UE, the SRS configuration for the uplink grant instance based ona value of an SRS resource indicator field associated with the uplinkgrant instance.
 24. The apparatus of claim 12, wherein the set of SRSconfigurations include a set of allowed SRS configurations for thelogical channel.
 25. A non-transitory computer-readable medium storinginstructions that, when executed by a processor, cause the processor toperform operations comprising: receiving, by a user equipment (UE), alogical channel prioritization (LCP) restriction configuration for alogical channel indicating a set of Sounding Reference Signal (SRS)configurations associated with the logical channel; receiving, by theUE, an uplink grant indicating an uplink grant instance and an SRSconfiguration for the uplink grant instance; and selecting, by the UE,the logical channel to use resources of the uplink grant instance basedin part on the set of SRS configurations and the SRS configuration forthe uplink grant instance; transmitting, by the UE, data via theselected logical channel, wherein the set of SRS configurationsassociated with the logical channel is a subset of a set of allowed SRSconfigurations for a plurality of logical channels including the logicalchannel; and transmitting, by the UE, second data via a second logicalchannel based on the set of allowed SRS configurations, the second dataincluding a second Packet Data Convergence Protocol (PDCP) Packet DataUnit (PDU), the second PDCP PDU generated based on duplicating a PDCPPDU corresponding to the data transmitted via the selected logicalchannel.
 26. An apparatus configured for wireless communication, theapparatus comprising: means for receiving a logical channelprioritization (LCP) restriction configuration for a logical channelindicating a set of Sounding Reference Signal (SRS) configurationsassociated with the logical channel; means for receiving an uplink grantindicating an uplink grant instance and an SRS configuration for theuplink grant instance; and means for selecting the logical channel touse resources of the uplink grant instance based in part on the set ofSRS configurations and the SRS configuration for the uplink grantinstance; means for transmitting data via the selected logical channel,wherein the set of SRS configurations associated with the logicalchannel is a subset of a set of allowed SRS configurations for aplurality of logical channels including the logical channel; and meansfor transmitting second data via a second logical channel based on theset of allowed SRS configurations, the second data including a secondPacket Data Convergence Protocol (PDCP) Packet Data Unit (PDU), thesecond PDCP PDU generated based on duplicating a PDCP PDU correspondingto the data transmitted via the selected logical channel.
 27. Thenon-transitory computer-readable medium of claim 25, wherein theinstructions that, when executed by the processor, further cause theprocessor to perform operations comprising: determining, by the UE, theSRS configuration for the uplink grant instance based on a value of anSRS resource indicator field associated with the uplink grant instance.28. The apparatus of claim 26, further comprising: means for determiningthe SRS configuration for the uplink grant instance based on a value ofan SRS resource indicator field associated with the uplink grantinstance.